D211101.txt 0.0.26 UTF-8 2023-12-05 *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* nfoWare/nfoWorks nfoTools ========================= VCRAYAPP: VC/C++ COMMAND-LINE RAYLIB APP DEVKIT ----------------------------------------------- VCrayApp consists of a Zip package for a software construction set to simplify command-line compiling of C/C++ language programs using Microsoft Windows developer tools and the raysan5/raylib library for graphical applications. VCrayApp is delivered in a form that can be confirmed for correct operation before customization as part of a specific project. MANIFEST D211101.txt this manifest and job-jar file index.md the web front page to this D211101 folio. Usage-2023-05-16-0939-VCrayApp-0.1.0.png latest Usage command result a/ D211101a: VCrayApp Setup D211101a/ D211101a: Tombstone (referenced from VCrayApp 0.0.0) b/ D211101b: VCrayApp Operation c/ D211101c: VCrayApp Verification/Deployment Lifecycle D211101c/ Tombstone for incorrect reference from VCrayApp.bat 0.0.0 when having a fixed "latest" was expected. Now it can simply point to 0.1.0 and the CHANGES. D211101d/ D211101d: VCrayApp 0.0.0 (alpha), preserved here because of references from VCrayApp-0.0.0.txt and other places. e/ D211101e: VCrayApp 0.1.0 (beta) f/ D211101f: VCrayApp Failure Codes *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* Copyright 2022-2023 Dennis E. Hamilton Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* ATTRIBUTION Hamilton, Dennis E. VCrayApp: VC/C++ Command-Line raylib App devKit. nfoTools development text file D211101.txt version 0.0.26 dated 2023-12-05, available on the Internet as a version of TODO * I need to make clear that not only is this focused on VC/C++ use of raylib, but until further notice we are sticking with plain-vanilla raylib with no alternative backends and only Desktop compilation targets. * Dig into devKits/WinDev/VCrayApp for more material and explanations here. * Refine with more internet browsable information and linked materials. * Verify hashes and signatures and document how it is done. * Appeal to skills and toolcraft on handling hashes and signatures, when available. * Distinguish between using a VCrayApp kit found in a distribution one is using versus incorporation in a distribution one is producing. There is also the middle case, inserting a VCrayApp kit in a project one wants to work on (a clone of). This is beyond testing and deployment though. This is customization. Need to ponder that. Be emphatic in the D211101d and D211101e subfolios. * Add link to T211002 on Visual Studio Native Build Tools and eventually have more on the VC/C++ compiler usage at that place, or a new Toolnote * Add link to T211102 on Git and GitHub and having more on that case. Those could be supplements. * Add link to T211001 on Visual Studio Code. Be certain to add a link to the documentation and maybe need to emphasize some things about trusted repositories. * Add D211101 to the title of index.md * Update status on the docs/dev/index.md page. * Determine whether there is a detached signature for VCrayApp.bat and also for anything in the cache. This is probably unnecessary and we have to deal with the fact that many of the cache\*.opt files may be modified but ideally not VCrayApp.bat itself. Mmm, except for %VCRAYEXE% and that will immediately break any signature. * Embedded use should be an advanced topic related to lifecycle management and such considerations. This is moderately acute when VCrayApp is embedded in a distribution, such as VCrayVerify. * Update the NOTE on section 2. * Mention "recent" raylib source-code release. This business is also important with respect to life-cycle. * There needs to be some links on using Windows File Explorer. Something general around usage by/for developers. * Use of the built-in Zip also needs to be described better elsewhere. * Use of the VC/C++ Command Line Compiler also needs a general tools place. * Link to Visual Studio Code. * Link to TortoiseGit tool. * Link to Git4Win and other Git materials. * Link to GitHub Windows Client for additional information. Feature that this is not required, and Git can be used directly as a command-line utility. * Link to GPG4Win and other generic GPG materials. * Establish that this material is effective as of, and applicable, to the 0.1.0 (beta) release of VCrayApp. * Mention libs as a prospect in the cache but not in src\*.c because we don't have a good way to parse that or any alternative %VCAPPSRC% value. So the only place for foreign libs is cache, which rather makes sense. * The creation of shortcuts and customized properties for the Developer Command Prompt needs to be introduced in some manner. *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* 0.0.26 2034-23-05T06:17Z TODO on confinement to plain DESKTOP raylib default. 0.0.25 2023-05-16T16:53Z Cleanup for VCrayApp-0.1.0 pre-release visibility 0.0.24 2023-05-07T20:24Z Complete the transpositions to new subfolder URLs 0.0.23 2023-05-07T19:04Z Complete D211101b/c/e transpositions 0.0.22 2023-05-07T17:32Z Complete movement and tombstoning of D211101a. 0.0.21 2023-05-07T01:21Z Expand TODOs with need for tombstones, preservation 0.0.20 2023-05-06T18:52Z TODOs on Folio restructuring 0.0.19 2023-04-30T17:22Z More TODO cleanup and document touch-ups 0.0.18 2023-04-29T19:13Z TODO touch-ups 0.0.17 2023-04-20T16:14Z More TODOs, not actual progress 0.0.16 2023-04-09T17:01Z Manage TODOs 0.0.15 2023-04-07T04:09Z Add fails/ to the manifest 0.0.14 2023-02-24T20:32Z Manage TODOs and preparations for 0.1.0 0.0.13 2023-02-10T18:41Z Introduce D211101e shadow and tidy up 0.0.12 2023-01-15T01:47Z Manage TODOs, recommend more tidying, linking 0.0.11 2023-01-14T23:40Z Manage TODOs, synchronize with D211101d 0.0.10 2023-01-14T10:51Z Manage TODOs, emphasizing alpha and incomplete materials 0.0.9 2023-01-12T17:02Z Manage TODOs, changing D211101c purpose 0.0.8 2023-01-12T05:18Z Manage TODOs 0.0.7 2023-01-12T03:15Z Add TODOs from review of current page 0.0.6 2023-01-02T22:07Z Manage TODOs, Alignment of D211101.txt and index.md 0.0.5 2023-01-02T18:58Z Review and TODO Touch-ups 0.0.4 2022-10-26T17:37Z Adjust for the desired version progression technique 0.0.3 2022-08-18T18:07Z expand for Setup and Operation 0.0.2 2022-08-16T22:39Z touch-ups and simplification 0.0.1 2022-06-10T00:47Z Anticipate D211101c and manage TODOs 0.0.0 2022-05-30T17:35Z Placeholder morphed from D161101.txt 0.0.5 and adjusted for getting started on making VCrayApp available. ***** end of D211101.txt *****